fix(docs): fix broken link to TypeScript Vue Plugin in console/atest-ui/README.md#731
Conversation
|
LinuxSuRen
added
documentation
LinuxSuRen
left a comment
LinuxSuRen
left a comment
There was a problem hiding this comment.
LGTM
However, please always create a new corresponding branch for each PR. See also the following explanation:
|
It will bring unrelated commits into your PRs if you use
|
|
Thank you for the reply. I have read the relevant guide in detail and studied the corresponding specifications. For example, currently, all changes in the repository I forked have been committed to the master branch. The next step should be to create a new local branch named fix-xxx-bug to make modifications, push it to my forked repository, and then submit a PR for the changes in this newly created fix-xxx-bug branch to the original repository. I have a few small questions: I noticed that Dependabot is responsible for many branches in the original repository. It seems amazing to learn about Dependabot's related technologies and the role of maintaining so many branches. Thanks again for your reply! |
|
Yes, some bots are helpful. The dependabot can find the latest dependencies. But we need to be careful before merging the dependency update. |
2 participants
What type of PR is this?
Very minor fix(docs): fix broken link to TypeScript Vue Plugin in console/atest-ui/README.md.
What this PR does / why we need it:
The old vscode‑typescript‑vue‑plugin (sometimes called “TypeScript Vue Plugin (Volar)”) has been removed and is no longer needed as a separate installation.
Volar (now the “Vue – Official” extension) includes all its features
The Vue team merged TypeScript support for Vue directly into Volar, making the separate plugin redundant.link to reddit